fix(@jest/resolve): Include stringifiedOptions in getModuleIDAsync #12766
+22
−4
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
I use native ESM with the
--experimental-vm-modules
flag. When upgrading to Jest 28,jest.unstable_mockModule
stopped working:I tracked this down to the mock detection failing due to
getModuleID
andgetModuleIDAsync
not generating identical IDs. In this casegetModuleIDAsync
did not append the stringified options, so the lookup using the ID as a key failed.There are other slight differences between
getModuleID
andgetModuleIDAsync
that might lead to similar issues.Test plan
jest.unstable_mockModule
followed by a dynamic import should resolve the mocked module